General Guidelines

Your instructor may have you use the team/breakoutrooms or stay in the classroom (and/or have the team record the presentations and submit mp4 files to myCourses as well as a link to the video uploaded to youtube - check with your instructor!).

Given the number of teams in your section and availability of a course assistant, you must plan on the length of your presentation to be only between10-12 minutes (for s2) or 12-15 minutes (for s4) to present and "defend" your project design and answer questions. Assume the audience is technically saavy and use software engineering language to present. All teammates are expected to participate.

We cannot stress this enough, get clarification from your instructor/client in advance so you know exactly what is expected from your team and you are not scrambling to prepare or violating the time allotment.

The point of this presentation is to describe the design choices that you made. The talk can generally follow the top down flow of your design documentation. Don't spend much time on what is common for all teams:

• Problem domain
• Requirements

You did not select the architecture, so don't justify it:

• Explain your understanding of the architectural tiers and their interactions
• Explain your philosophy for maintaining the architectural separation of concerns

Your documentation will provide many more details than you can give in your presentation. Provide visual support for the discussion of your design elements:

• You will need to show some class diagrams
• Use multiple class diagrams. A single one for the system is almost guaranteed to be unreadable.
• You may want to create class diagrams for the presentation that have less detail, i.e no attributes or methods.
• You should pick a significant feature and show how it flows through the system. This can be highlighted on your class diagram or be done with a sequence diagram after those are covered in class.

Be clear on the purpose for the slide

• Have your diagram target that level of information.

The areas that you think are most interesting are probably interesting to the audience too:

• Where your team had the most discussion
• Where you seek input on your decisions
• Areas that you are proud of:
  • You think it is unique in some way
  • You think it is an elegant design solution
  • The design made some aspect of implementation easier

You can also talk about an area where you had to make changes from an original design

• What was the problem with the original design?
• What prompted the change?

Sprint 4 Presentation - Transition Phase

Your Sprint 4 presentation will be your final presentation to your instructor and the class. You should plan for about 12 minutes total including time for questions at the end. Follow the general guidelines above, when you present the design of your term project including the following topics:

• Final domain model
• Architectural overview of the tiers and any subsystems within tiers
• Class and Sequence diagrams from key areas of your project
• Static Code Analysis highlights
• Recommendations for software architecture design improvements
• Address any future usability design improvements